An Improved User Requirements Notation (URN) Models’ Construction Approach

نویسندگان

چکیده

Semi-formal software techniques have been very successful in industry, government institutions and other areas such as academia. Arguably, they owe a large part of their success to graphical notation, which is more human-oriented than counterpart text-based formal notation techniques. However, ensuring the consistency between two or models one known challenges these This work looks closely at specific case User Requirements Notation (URN) technique. Although abstract model URN provides for link elements ensure its main components, namely, Goal-Oriented Requirement Language (GRL) Use Case Maps (UCM), effective implementation links yet be fully addressed. paper performs detailed analysis existing construction process proposes an improved with some guidelines ensure, by construction, correctness GRL UCM models. A study used throughout illustrate suggested solution.

برای دانلود رایگان متن کامل این مقاله و بیش از 32 میلیون مقاله دیگر ابتدا ثبت نام کنید

اگر عضو سایت هستید لطفا وارد حساب کاربری خود شوید

منابع مشابه

Consistency Analysis for User Requirements Notation Models

The User Requirements Notation (URN) is a standard modeling language that includes two complementary views, one for goals with the Goaloriented Requirement Language (GRL) and one for scenarios/processes with Use Case Maps (UCM). The URN standard, however, does not provide means of checking consistency between the GRL and UCM views, leading to models that are potentially erroneous. This paper pr...

متن کامل

Aspect Oriented User Requirements Notation

The Aspect-oriented URN (AoURN) [11] effort extends the User Requirements Notation (URN) [2, 14] with aspects. To date and to the best of our knowledge, no standardized framework unifying goal-oriented, scenario-based, and aspectoriented concepts exists. The goal of this research is to do this with minimal changes to URN in order to ensure that requirements engineers can continue working with f...

متن کامل

Capturing Non-functional Software Requirements Using the User Requirements Notation

Non-functional requirements (NFRs) are crucial software requirements that have be specified early in the software development process while eliciting the functional software requirements (FRs) [1,2]. NFRs can be viewed as additional constraints that have to be satisfied by the functional requirements. The non-satisfaction of NFRs is one of the main reasons for the failure of software projects. ...

متن کامل

Aspect-Oriented User Requirements Notation: Aspects in Goal and Scenario Models

Technologies based on aspects and applied at the early stages of software development allow requirements engineers to better encapsulate crosscutting concerns in requirements models. The Aspect-oriented User Requirements Notation (AoURN) extends the User Requirements Notation (URN) with aspects and thus unifies goal-oriented, scenariobased, and aspect-oriented concepts in one framework. Minimal...

متن کامل

Business process management with the user requirements notation

A number of recent initiatives in both academia and industry have sought to achieve improvements in e-businesses through the utilization of Business Process Management (BPM) methodologies and tools. However there are still some inadequacies that need to be addressed when it comes to achieving alignment between business goals and business processes. The User Requirements Notation (URN), recently...

متن کامل

ذخیره در منابع من


  با ذخیره ی این منبع در منابع من، دسترسی به آن را برای استفاده های بعدی آسان تر کنید

ژورنال

عنوان ژورنال: Systems

سال: 2023

ISSN: ['2079-8954']

DOI: https://doi.org/10.3390/systems11060301